feat: add support for stale/lock workflows#524
Merged
Conversation
utkuozdemir
reviewed
Jun 9, 2025
| - ubuntu-latest | ||
| steps: | ||
| - name: Lock old issues | ||
| uses: dessant/lock-threads@v5 |
Member
There was a problem hiding this comment.
This is not consistent with LockThreadsActionVersion, maybe needs re-kres?
Member
Author
There was a problem hiding this comment.
I forgot to use the constant, thanks for noticing this 🤦
utkuozdemir
approved these changes
Jun 9, 2025
Borrow the configuration/flow from Talos repo, where these flows run for a long time and pretty successfully manage stale issues/discussions/PRs. To disable it, use the following in `.kres.yaml`: ```yaml kind: common.Repository spec: skipStaleWorkflow: true ``` Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Member
Author
|
/m |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Borrow the configuration/flow from Talos repo, where these flows run for a long time and pretty successfully manage stale issues/discussions/PRs.
To disable it, use the following in
.kres.yaml: